Reducing arp/nd flooding in cloud environment

ABSTRACT

Aspects of the embodiments are directed to receiving an address resolution protocol (ARP) request message from a requesting virtual machine, the ARP request message comprising a request for a destination address for a destination virtual machine, wherein the destination address comprises one or both of a destination hardware address or a destination media access control address; augmenting the ARP request message with a network service header (NSH), the NSH identifying an ARP service function; and forwarding the augmented ARP request to the ARP service function.

FIELD

This disclosure pertains to reducing address resolution protocol (ARP) and/or neighbor discovery (ND) in a cloud environment.

BACKGROUND

Currently in Virtual Private cloud, Hybrid Cloud or Data center scenarios, it is common to see different Layer 2 network/sites are connected using various overlay technologies (like EVPN, VxLAN, NVO3, etc.). In these scenarios, the Overlay Edge Node (e.g. NVE, PE) uses dataplane based MAC learning and exchange the MAC reachability over BGP. The Overlay Edge node (e.g. NVE, PE) can also perform ND/ARP snooping for additional optimization and advertise the IP/MAC reachability info via BGP, so that any Edge Node (e.g. NVE, PE), upon receiving ND/ARP requests from connected L2 devices (e.g. Virtual Machines VMs) would check the local cache table for existing ND/ARP entries and reply directly to the connected L2 devices, if appropriate match is found. If there is no match found, then Edge Node would flood the request to remote Edge Nodes and wait for the reply.

FIG. 1 is a block diagram of an example network 100. In FIG. 1, a Host2 108 in L2Site2 110 has not originated any traffic. If a Host1 102 from L2Site1 104 is sending an ND/ARP request for Host2, the ND/ARP request will be flooded by network virtualization edge network element (NVE1) 106 to all remote NVE (NVE2 112 and NVE3 118 in this scenario), which in turn will flood the ND/ARP request to other connected L2 sites. The same flooding issue is observed if the MAC entry is timed out on the NVEs for any MAC. This flooding becomes a challenge in large scale data center deployments.

It is possible that an orchestrator network element, such as a controller, is made aware of the IP/MAC address of the network function virtualization (NFV)/virtual machine (VM) instances, thereby allowing controllers to exchange the IP/MAC address reachability details with adjacent NVEs. However, this still does not address the above flooding challenge, as NVEs are still required to rely on data plane (learning and/or ND/ARP snooping) and control plane (e.g. BGP advertisements /withdrawal).

BRIEF DESCRIPTION OF THE DRAWINGS

FIG. 1 is a block diagram of an example network topology. In FIG. 1, a Host2 in L2Site2 has not originated any traffic.

FIGS. 2A-2E are schematic diagrams of a network topology in accordance with embodiments of the present disclosure.

FIG. 3A-3B are schematic diagrams of a network topology with virtual machine migration in accordance with embodiments of the present disclosure.

FIG. 4 is a process flow diagram for reducing address protocol resolution flooding in accordance with embodiments of the present disclosure.

FIG. 5A-5D are schematic diagrams of a network topology that includes a border gateway protocol table in accordance with embodiments of the present disclosure.

FIG. 6 is a process flow diagram for reducing address protocol resolution flooding in accordance with embodiments of the present disclosure.

FIG. 7A illustrates a Service Function Chain (SFC), which may include an initial Classification function, as an entry point into a Service Function Path (SFP), according to some embodiments of the disclosure.

FIG. 7B-7C illustrate different service paths realized using service function chaining, according to some embodiments of the disclosure.

FIG. 8 shows a system view of a Service Chain Function-aware network element for prescribing a service path of a traffic flow, according to some embodiments of the disclosure.

FIG. 9 shows a system view of a service node, according to some embodiments of the disclosure.

DETAILED DESCRIPTION

This disclosure describes leveraging a controller's knowledge about the IP/MAC address of spawned VM/service function (SF)/NFV instances and prepopulate the same as an address resolution protocol service function (ARP-SF) on each L2 sites. NVE sniffs the ARP request from connected site and forwards the ARP to an ARP-SF after encapsulating the ARP request with a network service (NSH) header.

Aspects of the embodiments are directed to one or more computer readable storage media encoded with software comprising computer executable instructions and when the software is executed operable to receive an address resolution protocol (ARP) request message from a requesting virtual machine, the ARP request message comprising a request for a destination address for a destination virtual machine, wherein the destination address comprises one or both of a destination hardware address or a destination media access control address; augment the ARP request message with a network service header (NSH), the NSH identifying an ARP service function; and forward the augmented ARP request to the ARP service function.

In some embodiments, the software is further operable to receive an ARP reply message from the ARP service function; decapsulate a network service header from the ARP reply message; and forward the decapsulated ARP reply message to the requesting virtual machine, the ARP reply message including a destination address for a destination virtual machine.

In some embodiments, wherein the software is further operable to update a forwarding table with the destination address for the destination virtual machine.

In some embodiments, the software is further operable to determine, from the ARP reply message received from the ARP service function, that the destination address for the destination virtual machine is not present in an ARP service function database; and transmit an ARP request message to one or more network elements in a network.

Aspects of the embodiments are directed to a network element for performing address resolution, the network element comprising at least one memory element having instruction stored thereon; at least one processor coupled to the at least one memory element and configured to execute the instructions to cause the service classifier node to receive an address resolution protocol (ARP) request message from a requesting virtual machine, the ARP request message comprising a request for a destination address for a destination virtual machine, wherein the destination address comprises one or both of a destination hardware address or a destination media access control address; augment the ARP request message with a network service header (NSH), the NSH identifying an ARP service function; and forwarding the augmented ARP request to the ARP service function.

In some embodiments, the at least one processor configured to cause the network element to receive an ARP reply message from the ARP service function; decapsulate a network service header from the ARP reply message; and forward the decapsulated ARP reply message to the requesting virtual machine, the ARP reply message including a destination address for a destination virtual machine.

In some embodiments, the at least one processor configured to cause the network element to update a forwarding table with the destination address for the destination virtual machine.

In some embodiments, the network element comprises a network virtualization edge network element.

In some embodiments, the at least one processor configured to cause the network element to determine, from the ARP reply message received from the ARP service function, that the destination address for the destination virtual machine is not present in an ARP service function database; and transmit an ARP request message to one or more network elements in a network.

Aspects of the embodiments are directed to one or more computer readable storage media encoded with software comprising computer executable instructions and when the software is executed operable to receive, at an address resolution protocol (ARP) service function, an ARP request message from a network element; perform a lookup in an ARP database associated with the ARP service function; generate an ARP reply message; forward the ARP reply message to the network element.

In some embodiments, the software is further operable to determine the presence in the ARP database of a destination address for a destination virtual machine identified in the ARP request message, wherein the destination address comprises one or both of a destination hardware address or a destination media access control address; and augment the ARP reply message with the destination address for the destination virtual machine.

In some embodiments, the software is further operable to determine the presence in the ARP database of a destination address for a destination virtual machine identified in the ARP request message, wherein the destination address comprises one or both of a destination hardware address or a destination media access control address; determine that the virtual machine is a local virtual machine based, at least in part, on the destination address of the destination virtual machine; and ignore the ARP request message.

In some embodiments, determine that a destination address for a destination virtual machine identified in the ARP request message does not exist in the ARP database; wherein generating an ARP reply message comprises generating an ARP reply message that includes a network service header that indicates the absence of the destination address for the destination.

In some embodiments, the software is further operable to receive from a controller one or more virtual machine destination addresses, and for each virtual machine destination address, a corresponding virtual machine identifier; and storing the one or more virtual machine destination address and corresponding virtual machine identifier in a database, wherein the destination address comprises one or both of a destination hardware address or a destination media access control address.

Aspects of the embodiments are directed to a network element for performing address resolution, the network element comprising at least one memory element having instruction stored thereon; at least one processor coupled to the at least one memory element and configured to execute the instructions to cause the service classifier node to receive, at an address resolution protocol (ARP) service function, an ARP request message from a network element; perform a lookup in an ARP database associated with the ARP service function; generate an ARP reply message; forward the ARP reply message to the network element.

In some embodiments, the at least one processor configured to cause the network element to determine the presence in the ARP database of a destination address for a destination virtual machine identified in the ARP request message; and augment the ARP reply message with the destination address for the destination virtual machine; wherein the destination address comprises one or both of a destination hardware address or a destination media access control address.

In some embodiments, the at least one processor configured to cause the network element to determine the presence in the ARP database of a destination address for a destination virtual machine identified in the ARP request message; determine that the virtual machine is a local virtual machine based, at least in part, on the destination address of the destination virtual machine; and ignore the ARP request message; wherein the destination address comprises one or both of a destination hardware address or a destination media access control address.

In some embodiments, the at least one processor configured to cause the network element to determine that a destination address for a destination virtual machine identified in the ARP request message does not exist in the ARP database; wherein generating an ARP reply message comprises encapsulating the APR request message; setting a flag in the network service header to flood the APR request, and forwarding the ARP request message to the network element that includes a network service header that indicates the absence of the destination address for the destination.

In some embodiments, the at least one processor configured to cause the network element to receive from a controller one or more virtual machine destination addresses, and for each virtual machine destination address, a corresponding virtual machine identifier; and storing the one or more virtual machine destination address and corresponding virtual machine identifier in a database.

In some embodiments, wherein the destination address comprises one or both of an internet protocol (IP) or media access control (MAC) address.

Aspects of the embodiments are directed to an NVE that is configured to receive the ND/ARP request message from the requesting VM. The NVE can look up a BGP table for the destination address (hardware address or MAC address) information for the destination VM. The NVE can create a reply, and send the reply message to the VM. The NVE can also update the forwarding table, the entry of which would expire after some time period.

The ARP-SF replies back with the details if it has the same in local database. Else will signal the NVE to flood the request. Scalable and dynamic way of reducing the ARP flooding.

The idea is to dedicate one or more Service Functions (SF), dubbed as ND/ARP-SF that keeps track of IP/MAC details of each VM instance in local and remote L2 sites, and provide the IP/MAC reachability information to the Overlay Edge Node (e.g. NVE, PE) when requested using Network Services Header (NSH) mechanism.

Overlay Edge Node does NOT populate the IP/MAC reachability information in its forwarding table by default, until/unless there is a corresponding traffic. This is because the IP/MAC reachability details are outsourced to ND/ARP-SF.

ND/ARP-SF Service Function is populated with the IP/MAC details of each VM instance, after it is spun up, and deleted when VM instance is deleted. To make this happen (updating the IP/MAC details per VM), ND/ARP-SF communicates (using APIs (e.g. REST) preferably in pub/sub manner) with either Virtual Infra Manager (VIM) such as vCenter, Openstack, etc. or a controller such as Virtual Topology System (VTS), etc. depending on the deployment model.

Note that there could be more than one ND/ARP-SF and more than one VIM/Controllers for scale purposes. Controllers are typically used on top of VIM for scale purposes.

The IP/MAC reachability details are exchanged among the controllers of different sites using any (REST) API or BGPEVPN. This consolidated information is populated in ARP-SF.

FIGS. 2A-2E are schematic diagrams of a network topology 200 in accordance with embodiments of the present disclosure. Topology 200 includes a first site (Site1) 202. Site1 202 can include one or more instantiated virtual machines, such as VM1 206 a and VM9 206 b. Though shown as two VMs, any site can include a plurality of VM instantiations.

ND/ARP-SF Service Function is populated with the IP/MAC details of each VM instance, after it is spun up, and deleted when VM instance is deleted. To make this happen (updating the IP/MAC details per VM), ND/ARP-SF communicates (using APIs (e.g. REST) preferably in pub/sub manner) with a controller 240 (which can be either Virtual Infra Manager (VIM) such as vCenter, Openstack, etc. or a controller such as Virtual Topology System (VTS), etc. depending on the deployment model). The controller 240 can populate an ARP-SF database 210.

Site1 202 includes a network virtualization edge (NVE1) 204. A network Virtualization Edge (NVE) is a component in Network Virtualization Overlays Technology. An NVE can provide different types of virtualized network services to multiple tenants, i.e. an L2 service or an L3 service. Note that an NVE may be capable of providing both L2 and L3 services for a tenant.

An L2 NVE implements Ethernet LAN emulation, an Ethernet based multipoint service similar to an IETF VPLS, or EVPN service, where the Tenant Systems appear to be interconnected by a LAN environment over an L3 overlay. As such, an L2 NVE provides per-tenant virtual switching instance (L2 VNI), and L3 (IP/MPLS) tunneling encapsulation of tenant MAC frames across the underlay. Note that the control plane for an L2 NVE could be implemented locally on the NVE or in a separate control entity.

The site1 202 can also include an address resolution protocol service function (ARP-SF) 208. ARP-SF 208 can maintain or access an ARP-SF database that cross references IP addresses/MAC addresses and remote NVEs for destination address resolution.

Other sites, such as site2 212 and site 3 222 can include similar features. For example, site2 212 includes NVE2 214, VM2 216 (instantiated VM), and ARP-SF 218. Site3 222 includes NVE3 224, instantiated VM3 226, and ARP-SF 228. The sites can be connected through a cloud service provider 230. A controller 240 can provide orchestration and other control functions for each site or for all sites, collectively. Controller 240 can include a virtual infrastructure management (VIM) network element. In embodiments, the controller 240 can populate the APR-SF database 210. In embodiments, the ARP-SF database 210 can also be populated by the NVE forwarding table.

In the topology 200 shown in FIG. 2B, NVE1 204 can receive an ND/ARP request from a device (e.g., VM1 206 a in local L2 site1 202). In this example, the ND/ARP request can be a request for VM2 216 in L2 site2 212. NVE1 204 can encapsulate the request in a network service header (NSH). NVE1 204 can forward the encapsulated ND/ARP request towards the ARP-SF 208. In embodiments, the APR-SF 208 can also handle neighbor discovery (ND) requests.

As shown in FIG. 2C, the ARP-SF 208 can process the request by performing a lookup in database 210. If a match is found for VM2 in database 210, the ARP-SF 208 can generate the ND/ARP reply, encapsulate it with an NSH header (along with the remoteNVE associated with that VM entry, a VXLAN tunnel endpoint (VTEP), etc., in the NSH metadata) and unicast it to the NVE1 204.

NVE1 on receiving the reply can use the details (IP/MAC and remoteNVE in metadata) to update NVE1's forwarding table (e.g., cache table, shown in FIG. 3A), decapsulate the reply from the ARP-SF 208, and forward the ND/ARP reply towards the originating device (here, VM1 206 a). For example, ARP-SF 208 can reply back with {IP=10.1.1.2;MAC=2.2.2;remoteNVE=NVE2} to NVE1. NVE1 will program the details locally, decapsulate the network service header, and send the reply to VM1. By using stored information in the ARP-SF database 210, the NVE1 204 in this scenario can forgo flooding the ND/ARP request.

In embodiments, the NVE could be configured to not redirect the ND/ARP reply for certain ranges of IP prefixes to avoid having the NVE try to resolve requests originated in local sites (since the underlay or overlay could implicitly resolve such requests).

In some embodiments, the VM1 can floods a request for VM10 206 n, which is in the L2 Site1 202. All nodes in L2Site1 (including NVE1 and VM10) will receive the request. NVE1 will encapsulate with NSH header and forward to ARP-SF. Since VM10 is local, ARP-SF will simply ignore it. In the meantime, VM10 206 n will reply back to VM1 206 a with the address resolution.

FIG. 2D is a schematic diagram of a network topology in accordance with embodiments of the present disclosure wherein the ARP-SF 208 cannot resolve the ND/ARP request (e.g., because the ARP-SF 208 does not have MAC details in database 210). As shown in FIG. 2D, VM1 206 a sends a request for VM300 206 n. NVE1 204 can check its cache (forwarding) table for VM300 information. When the NVE1 204 does not have IP/MAC information for VM300, NVE1 can encapsulate the ARP request with an NSH header and forward the encapsulated APR request to ARP-SF 208.

In FIG. 2E, ARP-SF 208, after receiving the request from NVE1 204, will reply back with relevant details (including a flag in Metadata) signaling that it does not have any local entry for VM300. NVE1 204, after receiving such reply will flood the APR request to all remote NVEs (e.g., NVE2 214 and NVE3 224). This is a backward compatible way and will not cause any packet loss if ARP-SF 208 has not been updated with the MAC details.

The above concept does not require the NVE to be loaded with details of all other nodes in remote sites. Instead uses a scalable manner of spinning ARP-SF instances as required and have the NVE to redirect the request to ARP-SF and thereby reduce the flooding.

VM Move Scenario:

FIGS. 3A-3B are schematic diagrams of a network topology for reducing address resolution flooding for a virtual machine that has moved in accordance with embodiments of the present disclosure. In FIG. 3A, VM2 216 undergoes VM migration from site2 212 to site3 222. In embodiments, VM migration does not involve any change in IP/MAC associated instance. For example, VM2 216 from site2 212 can migrate to site3 (shown as VM2 227 in FIG. 3B). So during such scenarios, all ARP-SFs in different L2Sites will be programmed with new details (like the remote NVE details, etc.). For example, a local ARP-SF 228 can inform a central controller (e.g., VIM/controller), which can publish the move to other ARP-SFs.

When VM1 206 a sends a new ARP request for the MAC address for VM2 216 within an L2 site and if the local NVE1 204 does not have an entry for that MAC in its forwarding table, then NVE1 204 simply relies on the process (as described above) to learn the latest binding from ARP-SF 208.

However, if NVE1 204 does have an entry (which might be stale) for that MAC for VM2 216 in its forwarding table (pointing to the old remote NVE2 214), then one of two embodiments could apply (depending on Stateful or Stateless ARP-SF logic):

(a) Stateful ARP-SF: a stateful ARP-SF would retain the identity of each NVE that interacted with ARP-SF for each IP/MAC. The stateful ARP-SF could send the updated IP/MAC: NVE binding info to NVE on an unsolicited basis using a NSH (new flag could be set), as soon as ARP-SF learns about the updated info (from the controller 240).

(b) Stateless ARP-SF: A stateless ARP-SF does not keep track of which NVE interacted for what IP/MAC:NVE binding. The NVE would follow the current dataplane learning (and flooding) to update its local forwarding table. Note that given the redirection by remote NVE, there would be minimal or no loss.

The above concepts do not require the NVE to be loaded with details of all other nodes in remote sites. Instead, APR-SF instances are spun up scalably and as required and have the NVE to redirect the request to ARP-SF to reduce the flooding.

When a VM is torn down, the VIM/controller 240 can delete the entry from the local ARP-SF instance or from any ARP-SF instance under the control of the VIM/controller 240. In some embodiments, an ARP-SF instance that has an entry deleted can alert other ARP-SF instances to delete entries.

FIG. 4 is a process flow diagram 400 for reducing address protocol resolution flooding in accordance with embodiments of the present disclosure. A virtual machine can send an ND/ARP request to an NVE. The NVE can receive the ND/ARP request from the VM (402). The NVE can encapsulate the ND/ARP request with a network service header (NSH) for an ARP-SF instance common to the L2 site of the VM (404). The NVE can forward the encapsulated ND/ARP request to the ARP-SF (406).

The ARP-SF can look up a destination address for the destination VM from a database stored with, associated with, or accessible by the ARP-SF (408). If the address is not in the table, the ARP-SF can generate a reply with a flag in the reply metadata indicating there is no entry for the destination address for the destination VM (412). The ARP-SF can send the reply to the NVE. The NVE can flood the ND/ARP to other NVEs in the network.

If the address is in the ARP-SF table, the ARP-SF can determine whether the address is local to the site of the requesting VM (416). If the destination VM is local, then the ARP-SF can ignore the ND/ARP request because the local VM will respond to the requesting VM (418).

If the destination VM is not local, then the ARP-SF can generate an ARP reply (420). The ARP-SF can encapsulate the ARP reply with an NSH header (along with the remoteNVE associated with that entry in the NSH metadata). The ARP-SF can unicast the encapsulated ARP reply to NVE that redirected the ND/ARP request (422).

At the NVE, the NVE can decapsulate the ARP reply and forward the ARP reply to the requesting VM (424). The NVE can also update its forwarding table with the address in the ARP reply.

FIG. 5A-5D are schematic diagrams of a network topology 500 that includes a border gateway protocol table 510 in accordance with embodiments of the present disclosure. FIG. 5A is a schematic diagram illustrating an overview of the BGP scenario. In scenarios where the number of IP/MAC to be retained is not at massive scale, if all the IP/MAC address reachability are kept in BGP table 510 associated with NVE/PE routers, then (ARP-SF) could be eliminated in these scenarios. The IP/MAC addresses are not installed in the NVE forwarding tables (at first), as well as not advertised further (so remote MAC addresses are not advertised locally).

In that case, the NVE 504 would receive the IP/MAC details from the controller 540 and populate in BGP table 510 (or other local control plane table). VM1 506 would send the ARP to NV/PE1 504, and NV/PE1 504 would look into border gate protocol (BGP) table 510 for that destination IP. If the address exists in the BGP table 510, then the NVE 504 can use the incoming ARP request as a trigger to install the IP/MAC address in the forwarding table 508 of the NVE 504. The NVE 504 can send the ARP reply to VM1 506.

After not being used for a predetermined amount of time, the address information can be purged from forwarding table, but not from the BGP table 510 unless the controller 540 updates the BGP table 510 due to VM tear down/spin up and/or VM migration.

In FIG. 5B, a controller 540 can update BGP tables 510 a, 510 b, and 510 c. The controller 540 can update the local site MAC details to NVE nodes' BGP tables.

In FIG. 5C, VM1 506 sends an ARP request message to the NVE 504. In FIG. 5D, the NVE checks the BGP table 572. The NVE1 504 installs the BGP entry into the forwarding table and replies back to VM1.

FIG. 6 is a process flow diagram 600 for reducing address protocol resolution flooding in accordance with embodiments of the present disclosure. The NVE can receive an ND/ARP request from a VM (602). The NVE can perform a lookup for a destination address for destination VM in a BGP table (604). The BGP table can be populated with VM addresses and corresponding VM identification information by the VIM/Controller. The NVE can create an ND/ARP reply with the destination address (606). The NVE can update its forwarding table with the address for the destination VM (608). The NVE can remove the destination address for the VM after the expiration of a predetermined time period (610).

Basics of Network Service Chaining or Service Function Chains in a Network

To accommodate agile networking and flexible provisioning of network nodes in the network, Service Function Chains (SFC) can be used to ensure an ordered set of Service Functions (SF) to be applied to packets and/or frames of a traffic flow. SFCs provides a method for deploying SFs in a way that enables dynamic ordering and topological independence of those SFs. A service function chain can define an ordered set of service functions that is applied to packets and/or frames of a traffic flow, where the ordered set of service functions are selected as a result of classification. The implied order may not be a linear progression as the architecture allows for nodes that copy to more than one branch. The term service chain is often used as shorthand for service function chain.

FIG. 7A illustrates a Service Function Chain (SFC), which may include an initial service classification function 702, as an entry point into a Service Function Path (SFP) 704 (or service path). The (initial) service classification function 702 prescribes a service path, and encapsulates a packet or frame with the service path information which identifies the service path. The classification potentially adds metadata, or shared context, to the SFC encapsulation part of the packet or frame. The service function path 704 may include a plurality of service functions (shown as “SF1”, . . . “SFN”).

A service function can be responsible for specific treatment of received packets. A service function can act at the network layer or other OSI layers (e.g., application layer, presentation layer, session layer, transport layer, data link layer, and physical link layer). A service function can be a virtual instance or be embedded in a physical network element such as a service node. When a service function or other modules of a service node is executed by the at least one processors of the service node, the service function or other modules can be configured to implement any one of the methods described herein. Multiple service functions can be embedded in the same network element. Multiple instances of the service function can be enabled in the same administrative SFC-enabled domain. A non-exhaustive list of SFs includes: firewalls, WAN and application acceleration, Deep Packet Inspection (DPI), server load balancers, NAT44, NAT64, HOST_ID injection, HTTP Header Enrichment functions, TCP optimizer, etc. An SF may be SFC encapsulation aware, that is it receives, and acts on information in the SFC encapsulation, or unaware in which case data forwarded to the service does not contain the SFC encapsulation.

A Service Node (SN) can be a physical network element (or a virtual element embedded on a physical network element) that hosts one or more service functions (SFs) and has one or more network locators associated with it for reachability and service delivery. In many standardization documents, “service functions” can refer to the service nodes described herein as having one or more service functions hosted thereon. Service Function Path (SFP) (or sometimes referred simply as service path) relates to the instantiation of a SFC in the network. Packets follow a service path from a classifier through the requisite service functions.

FIGS. 7B-7C illustrate different service paths realized using service function chaining. These service paths can be implemented by encapsulating packets of a traffic flow with a network service header (NSH) or some other suitable packet header which specifies a desired service path (e.g., by identifying a particular service path using service path information in the NSH). In the example shown in FIG. 7B, a service path 720 can be provided between end point 760 and endpoint 780 through service node 706 and service node 710. In the example shown in FIG. 7C, a service path 730 (a different instantiation) can be provided between end point 770 and endpoint 790 through service node 706, service node 708, and service node 712.

Network Service Header (NSH) Encapsulation

Generally speaking, an NSH includes service path information, and NSH is added to a packet or frame. For instance, an NSH can include a data plane header added to packets or frames. Effectively, the NSH creates a service plane. The NSH includes information for service chaining, and in some cases, the NSH can include metadata added and/or consumed by service nodes or service functions. The packets and NSH are encapsulated in an outer header for transport. To implement a service path, a network element such as a service classifier (SCL) or some other suitable SFC-aware network element can process packets or frames of a traffic flow and performs NSH encapsulation according to a desired policy for the traffic flow.

FIG. 8 shows a system view of SFC-aware network element, e.g., such as a (initial) service classifier (SCL), for prescribing a service path of a traffic flow, according to some embodiments of the disclosure. Network element 802 includes processor 804, (computer-readable non-transitory) memory 806 for storing data and instructions. Furthermore, network element 802 includes service classification function 808 and service header encapsulator 810 (both can be provided by processor 804 when processor 804 executes the instructions stored in memory 806).

The service classification function 808 can process a packet of a traffic flow and determine whether the packet requires servicing and correspondingly which service path to follow to apply the appropriate service. The determination can be performed based on business policies and/or rules stored in memory 806. Once the determination of the service path is made, service header encapsulator 810 generates an appropriate NSH having identification information for the service path and adds the NSH to the packet. The service header encapsulator 810 provides an outer encapsulation to forward the packet to the start of the service path. Other SFC-aware network elements are thus able to process the NSH while other non-SFC-aware network elements would simply forward the encapsulated packets as is. Besides inserting an NSH, network element 802 can also remove the NSH if the service classification function 808 determines the packet does not require servicing.

Network Service Headers

A network service header (NSH) can include a (e.g., 64-bit) base header, and one or more context headers. Generally speaking, the base header provides information about the service header and service path identification (e.g., a service path identifier), and context headers can carry opaque metadata (such as the metadata described herein reflecting the result of classification). For instance, an NSH can include a 4-byte base header, a 4-byte service path header, and optional context headers. The base header can provide information about the service header and the payload protocol. The service path header can provide path identification and location within a path. The (variable length) context headers can carry opaque metadata and variable length encoded information. The one or more optional context headers make up a context header section in the NSH. For instance, the context header section can include one or more context header fields having pieces of information therein, describing the packet/frame. Based on the information in the base header, a service function of a service node can derive policy selection from the NSH. Context headers shared in the NSH can provide a range of service-relevant information such as traffic classification. Service functions can use NSH to select local service policy.

Service Nodes and Proxy Nodes

Once properly encapsulated, the packet having the NSF is then forwarded to one or more service nodes where service(s) can be applied to the packet/frame. FIG. 9 shows a system view of a service node, according to some embodiments of the disclosure. Service node 900, generally a network element, can include processor 902, (computer-readable non-transitory) memory 904 for storing data and instructions. Furthermore, service node 900 includes service function(s) 906 (e.g., for applying service(s) to the packet/frame, classifying the packet/frame) and service header processor 908. The service functions(s) 906 and service header processor 906 can be provided by processor 902 when processor 902 executes the instructions stored in memory 904. Service header processor 908 can extract the NSH, and in some cases, update the NSH as needed. For instance, the service header processor 908 can decrement the service index if a service index=0 is used to indicate that a packet is to be dropped by the service node 900. In another instance, the service header processor 908 or some other suitable module provide by the service node can update context header fields if new/updated context is available.

Within the context of the application, “metadata” refers to one or more pieces of information (e.g., bits of data, encoded values) in a context header section of a network service header. Metadata can refer to contents of the entire context header section, which can include the contents of one or more context header fields describing various attributes of the packet/frame. Metadata can also refer to contents of one individual context header field or a subset of context header fields in the context header section.

Moreover, the terms “first service node” and “second service node” does not necessarily imply that the “first service node” and the “second service node” are the first and second service nodes at the beginning of the service path that the packet/frame reaches as the packet/frame traverses over the service path. For instance, the first service node can be any suitable one of the service nodes among many service nodes in the service path (e.g., third one the packet/frame reaches as it traverses the service path, fourth one, fifth one, etc.). The second service node can be any suitable one of the service node(s) subsequent to the first service node downstream in the service path.

Within the context of the disclosure, a network used herein represents a series of points, nodes, or network elements of interconnected communication paths for receiving and transmitting packets of information that propagate through a communication system. A network offers communicative interface between sources and/or hosts, and may be any local area network (LAN), wireless local area network (WLAN), metropolitan area network (MAN), Intranet, Extranet, Internet, WAN, virtual private network (VPN), or any other appropriate architecture or system that facilitates communications in a network environment depending on the network topology. A network can comprise any number of hardware or software elements coupled to (and in communication with) each other through a communications medium.

In one particular instance, the architecture of the present disclosure can be associated with a service provider deployment. In other examples, the architecture of the present disclosure would be equally applicable to other communication environments, such as an enterprise wide area network (WAN) deployment, The architecture of the present disclosure may include a configuration capable of transmission control protocol/internet protocol (TCP/IP) communications for the transmission and/or reception of packets in a network.

As used herein in this Specification, the term ‘network element’ is meant to encompass any of the aforementioned elements, as well as servers (physical or virtually implemented on physical hardware), machines (physical or virtually implemented on physical hardware), end user devices, routers, switches, cable boxes, gateways, bridges, loadbalancers, firewalls, inline service nodes, proxies, processors, modules, or any other suitable device, component, element, proprietary appliance, or object operable to exchange, receive, and transmit information in a network environment. These network elements may include any suitable hardware, software, components, modules, interfaces, or objects that facilitate the network service header features/operations thereof. This may be inclusive of appropriate algorithms and communication protocols that allow for the effective exchange of data or information.

In one implementation, nodes with NSH capabilities may include software to achieve (or to foster) the functions discussed herein for providing the NSH-related features/functions where the software is executed on one or more processors to carry out the functions. This could include the implementation of instances of service functions, service header processors, metadata augmentation modules and/or any other suitable element that would foster the activities discussed herein. Additionally, each of these elements can have an internal structure (e.g., a processor, a memory element, etc.) to facilitate some of the operations described herein. In other embodiments, these functions may be executed externally to these elements, or included in some other network element to achieve the intended functionality. Alternatively, these nodes may include software (or reciprocating software) that can coordinate with other network elements in order to achieve the functions described herein. In still other embodiments, one or several devices may include any suitable algorithms, hardware, software, components, modules, interfaces, or objects that facilitate the operations thereof.

In certain example implementations, the NSH-related functions outlined herein may be implemented by logic encoded in one or more non-transitory, tangible media (e.g., embedded logic provided in an application specific integrated circuit [ASIC], digital signal processor [DSP] instructions, software [potentially inclusive of object code and source code] to be executed by one or more processors, or other similar machine, etc.). In some of these instances, one or more memory elements can store data used for the operations described herein. This includes the memory element being able to store instructions (e.g., software, code, etc.) that are executed to carry out the activities described in this Specification. The memory element is further configured to store databases or metadata disclosed herein. The processor can execute any type of instructions associated with the data to achieve the operations detailed herein in this Specification. In one example, the processor could transform an element or an article (e.g., data) from one state or thing to another state or thing. In another example, the activities outlined herein may be implemented with fixed logic or programmable logic (e.g., software/computer instructions executed by the processor) and the elements identified herein could be some type of a programmable processor, programmable digital logic (e.g., a field programmable gate array [FPGA], an erasable programmable read only memory (EPROM), an electrically erasable programmable ROM (EEPROM)) or an ASIC that includes digital logic, software, code, electronic instructions, or any suitable combination thereof.

Any of these elements (e.g., the network elements, service nodes, etc.) can include memory elements for storing information to be used in achieving the NSH-related features, as outlined herein. Additionally, each of these devices may include a processor that can execute software or an algorithm to perform the NSH-related features as discussed in this Specification. These devices may further keep information in any suitable memory element [random access memory (RAM), ROM, EPROM, EEPROM, ASIC, etc.], software, hardware, or in any other suitable component, device, element, or object where appropriate and based on particular needs. Any of the memory items discussed herein should be construed as being encompassed within the broad term ‘memory element.’ Similarly, any of the potential processing elements, modules, and machines described in this Specification should be construed as being encompassed within the broad term ‘processor.’ Each of the network elements can also include suitable interfaces for receiving, transmitting, and/or otherwise communicating data or information in a network environment.

Additionally, it should be noted that with the examples provided above, interaction may be described in terms of two, three, or four network elements. However, this has been done for purposes of clarity and example only. In certain cases, it may be easier to describe one or more of the functionalities of a given set of flows by only referencing a limited number of network elements. It should be appreciated that the systems described herein are readily scalable and, further, can accommodate a large number of components, as well as more complicated/sophisticated arrangements and configurations. Accordingly, the examples provided should not limit the scope or inhibit the broad techniques of using and augmenting NSH metadata, as potentially applied to a myriad of other architectures.

It is also important to note that the various steps described herein illustrate only some of the possible scenarios that may be executed by, or within, the nodes with NSH capabilities described herein. Some of these steps may be deleted or removed where appropriate, or these steps may be modified or changed considerably without departing from the scope of the present disclosure. In addition, a number of these operations have been described as being executed concurrently with, or in parallel to, one or more additional operations. However, the timing of these operations may be altered considerably. The preceding operational flows have been offered for purposes of example and discussion. Substantial flexibility is provided by nodes with NSH capabilities in that any suitable arrangements, chronologies, configurations, and timing mechanisms may be provided without departing from the teachings of the present disclosure.

It should also be noted that many of the previous discussions may imply a single client-server relationship. In reality, there is a multitude of servers in the delivery tier in certain implementations of the present disclosure. Moreover, the present disclosure can readily be extended to apply to intervening servers further upstream in the architecture, though this is not necessarily correlated to the ‘m’ clients that are passing through the ‘n’ servers. Any such permutations, scaling, and configurations are clearly within the broad scope of the present disclosure.

Numerous other changes, substitutions, variations, alterations, and modifications may be ascertained to one skilled in the art and it is intended that the present disclosure encompass all such changes, substitutions, variations, alterations, and modifications as falling within the scope of the appended claims. In order to assist the United States Patent and Trademark Office (USPTO) and, additionally, any readers of any patent issued on this application in interpreting the claims appended hereto, Applicant wishes to note that the Applicant: (a) does not intend any of the appended claims to invoke paragraph six (6) of 35 U.S.C. section 112 as it exists on the date of the filing hereof unless the words “means for” or “step for” are specifically used in the particular claims; and (b) does not intend, by any statement in the specification, to limit this disclosure in any way that is not otherwise reflected in the appended claims. 

What is claimed is:
 1. One or more computer readable storage media encoded with software comprising computer executable instructions and when the software is executed operable to: receive an address resolution protocol (ARP) request message from a requesting virtual machine, the ARP request message comprising a request for a destination address for a destination virtual machine, wherein the destination address comprises one or both of a destination hardware address or a destination media access control address; augment the ARP request message with a network service header (NSH), the NSH identifying an ARP service function; and forward the augmented ARP request to the ARP service function.
 2. The one or more computer readable storage media of claim 1, wherein the software is further operable to: receive an ARP reply message from the ARP service function; decapsulate a network service header from the ARP reply message; and forward the decapsulated ARP reply message to the requesting virtual machine, the ARP reply message including a destination address for a destination virtual machine.
 3. The one or more computer readable storage media of claim 2, wherein the software is further operable to: update a forwarding table with the destination address for the destination virtual machine.
 4. The one or more computer readable storage media of claim 1, wherein the software is further operable to: determine, from the ARP reply message received from the ARP service function, that the destination address for the destination virtual machine is not present in an ARP service function database; and transmit an ARP request message to one or more network elements in a network.
 5. A network element for performing address resolution, the network element comprising: at least one memory element having instruction stored thereon; at least one processor coupled to the at least one memory element and configured to execute the instructions to cause the service classifier node to: receive an address resolution protocol (ARP) request message from a requesting virtual machine, the ARP request message comprising a request for a destination address for a destination virtual machine, wherein the destination address comprises one or both of a destination hardware address or a destination media access control address; augment the ARP request message with a network service header (NSH), the NSH identifying an ARP service function; and forwarding the augmented ARP request to the ARP service function.
 6. The network element of claim 5, the at least one processor configured to cause the network element to: receive an ARP reply message from the ARP service function; decapsulate a network service header from the ARP reply message; and forward the decapsulated ARP reply message to the requesting virtual machine, the ARP reply message including a destination address for a destination virtual machine.
 7. The network element of claim 6, the at least one processor configured to cause the network element to update a forwarding table with the destination address for the destination virtual machine.
 8. The network element of claim 5, wherein the network element comprises a network virtualization edge network element.
 9. The network element of claim 6, the at least one processor configured to cause the network element to: determine, from the ARP reply message received from the ARP service function, that the destination address for the destination virtual machine is not present in an ARP service function database; and transmit an ARP request message to one or more network elements in a network.
 10. One or more computer readable storage media encoded with software comprising computer executable instructions and when the software is executed operable to: receive, at an address resolution protocol (ARP) service function, an ARP request message from a network element; perform a lookup in an ARP database associated with the ARP service function; generate an ARP reply message; forward the ARP reply message to the network element.
 11. The one or more computer readable storage media of claim 10, wherein the software is further operable to: determine the presence in the ARP database of a destination address for a destination virtual machine identified in the ARP request message, wherein the destination address comprises one or both of a destination hardware address or a destination media access control address; and augment the ARP reply message with the destination address for the destination virtual machine.
 12. The one or more computer readable storage media of claim 10, wherein the software is further operable to: determine the presence in the ARP database of a destination address for a destination virtual machine identified in the ARP request message, wherein the destination address comprises one or both of a destination hardware address or a destination media access control address; determine that the virtual machine is a local virtual machine based, at least in part, on the destination address of the destination virtual machine; and ignore the ARP request message.
 13. The one or more computer readable storage media of claim 10, wherein the software is further operable to: determine that a destination address for a destination virtual machine identified in the ARP request message does not exist in the ARP database; wherein generating an ARP reply message comprises generating an ARP reply message that includes a network service header that indicates the absence of the destination address for the destination.
 14. The one or more computer readable storage media of claim 10, wherein the software is further operable to receive from a controller one or more virtual machine destination addresses, and for each virtual machine destination address, a corresponding virtual machine identifier; and storing the one or more virtual machine destination address and corresponding virtual machine identifier in a database, wherein the destination address comprises one or both of a destination hardware address or a destination media access control address.
 15. A network element for performing address resolution, the network element comprising: at least one memory element having instruction stored thereon; at least one processor coupled to the at least one memory element and configured to execute the instructions to cause the service classifier node to: receive, at an address resolution protocol (ARP) service function, an ARP request message from a network element; perform a lookup in an ARP database associated with the ARP service function; generate an ARP reply message; forward the ARP reply message to the network element.
 16. The network element of claim 15, the at least one processor configured to cause the network element to determine the presence in the ARP database of a destination address for a destination virtual machine identified in the ARP request message; and augment the ARP reply message with the destination address for the destination virtual machine; wherein the destination address comprises one or both of a destination hardware address or a destination media access control address.
 17. The network element of claim 15, the at least one processor configured to cause the network element to determine the presence in the ARP database of a destination address for a destination virtual machine identified in the ARP request message; determine that the virtual machine is a local virtual machine based, at least in part, on the destination address of the destination virtual machine; and ignore the ARP request message; wherein the destination address comprises one or both of a destination hardware address or a destination media access control address.
 18. The network element of claim 15, the at least one processor configured to cause the network element to: determine that a destination address for a destination virtual machine identified in the ARP request message does not exist in the ARP database; wherein generating an ARP reply message comprises encapsulating the APR request message; setting a flag in the network service header to flood the APR request, and forwarding the ARP request message to the network element that includes a network service header that indicates the absence of the destination address for the destination.
 19. The network element of claim 15, the at least one processor configured to cause the network element to: receive from a controller one or more virtual machine destination addresses, and for each virtual machine destination address, a corresponding virtual machine identifier; and storing the one or more virtual machine destination address and corresponding virtual machine identifier in a database.
 20. The network element of claim 15, wherein the destination address comprises one or both of an internet protocol (IP) or media access control (MAC) address. 